Oliver Fels (Oliver@stanley.zebra.fh-weingarten.de) wrote:
: Am Mon, 15 Jan 96 11:39:48 MST machte sich Ish Hallin die Mⁿhe, in die
: Gruppe comp.sys.amiga.applications folgende Nachricht zu mei▀eln:
[...]
: > Probably no one will believe me on this, but IBrowse hung up my system
: > more than AMosaic ever has. Probably due to memory problems (I have 1
: > meg chip, 2 megs fast, which gets eaten up quickly between MUI, AmiTCP,
: > Ibrowse, and the JPEG datatype), but IBrowse would always crash whenever
: Let me tell you, in those times, 2 Megs are much too less for everything.
: Don┤t wonder. And don┤t mind programs crashing under those circumstances.
This is absurd! It is unacceptable for a program _ever_ to crash because it runs out of memory. If the operating system runs very low on memory it is possible that eventually there is no way out and a crash will ensue, but AmigaOS is now very well protected against this happening. If a program is unable to allocate sufficient memory for an operation it should simply abort the operation, or at least exit gracefully. This sort of program behaviour reminds me of c0d3rz...
--
Ben Hutchings, student. Finger me on worc0223@sable.ox.ac.uk for various info.
